docs: Update legacy auth migration guide to 4.0#604
Merged
Conversation
Swiftaxe
reviewed
Jun 15, 2026
Swiftaxe
left a comment
Swiftaxe
left a comment
Collaborator
There was a problem hiding this comment.
Inconsistency in versioning. See comments.
Swiftaxe
reviewed
Jun 15, 2026
Contributor
|
Needs a rebase to fix the conflict. |
developerjamiu
added
enhancement
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
…uth-guide-to-4 # Conflicts: # docs/11-upgrading/03-migrate-from-legacy-auth.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the legacy auth migration guide from 3.5 to 4.0: version pins, prose, and the link text to the upgrade guide. The page title (
Migrate from legacy serverpod_auth), the 3.4 from-version, and the SDK constraints are unchanged. The link path to the upgrade guide is kept so it keeps resolving.Note: the "Before you start" list still says the auth packages are "still beta" while pinning
4.0.0. If the auth stack ships stable with 4.0, that caveat should be trimmed; if it stays beta, the pins should be the beta version. Happy to adjust either way.Part of #584